Pull Request Checklist

• Have you updated the documentation, if impacted (e.g. docs.status.im)?

Not sure why we build for x86 and x86_64 considering almost no one uses x86 and we exclude the libraries for x86_64 here anyway:
https://github.com/status-im/status-react/blob/131b423a0acb92618192be17a92a9e51feda592e/android/app/build.gradle#L178
Maybe there's some reason I'm missing.

Jenkins Builds

100% of end-end tests have passed

Total executed tests: 49
Failed tests: 0
Passed tests: 49

Passed tests (49)

100% of end-end tests have passed

Total executed tests: 49
Failed tests: 0
Passed tests: 49

Passed tests (49)

@jakubgs is it expected? Android 8

realm strikes again 😭

realm/realm-js#1187

realm/realm-js#1187 (comment)

as @abury said, downgrading to 2.2.8 resolved the issue.

Also:

realm/realm-js#1187 (comment)

use this only if you're not planning on releasing a 64 bits version of your app

Great solution, nice.

Upgrading Realm really might help.

@jakubgs sounds like should help me market my PR :)

@asemiankevich can you please check it out now? I've rebased it on the changes introduced by #8336.

@jakubgs are there any news for this PR? I can see you've added "release" label recently but there are no new builds/updates. Do you expect to add them soon? cc @rachelhamlin

@annadanchenko I don't know how to fix this.

If you look at facebook/react-native#24261 there are still people there complaining that 64 bit builds do not work due to react-native, I do not know what to do about that.

@annadanchenko I think an Android dev should take over this task, because I don't know enough about Android apps to understand why enabling arm64-v8a architecture in builds makes it crash.

I thought the issue was the old JSC that was used in React-Native before 0.59.10, but apparently not.

so it doesn't work on samsung s10 as well, but i've tried it on readmi note 3 and it works randomly sometimes it stucks in different places (logo screen, generating accounts, or request messages), but sometimes it works pretty well
here are the logs when it gets stuck on logo screen https://gist.github.com/flexsurfer/94d5d67eb3880d2c2a62708b50c660b7
@jakubgs @pombeirp could you take a look?

these logs when it doesn't get stuck
https://gist.github.com/flexsurfer/b5824a0a1828ad28fc2d7aefa33e6074

could you take a look?

Those logs tell me nothing, I'm not an android dev.

Why are you adding x86-64 to env.NDK_ABI_FILTERS in ci/android.groovy?
My understanding is that x86* architecture are only useful for simulators, so they are not necessary for builds that are supposed to run on actual devices, is that incorrect?

@jakubgs i'm not sure https://medium.com/@andriidrozdov/reactnative-and-android-64-bit-new-google-play-market-rules-what-to-do-584b067d6f1a
IMPORTANT. Insure that in include and versionCodes you have "arm64-v8a" and "x86-64".

80% of end-end tests have passed

Total executed tests: 44
Failed tests: 9
Passed tests: 35

Failed tests (9)

Passed tests (35)

IMPORTANT. Insure that in include and versionCodes you have "arm64-v8a" and "x86-64".

Incorrect:

Enabling builds for your native code is as simple as adding the arm64-v8a and/or x86_64, depending on the architecture(s) you wish to support, to the ndk.abiFilters setting in your app's build.gradle file.

https://developer.android.com/distribute/best-practices/develop/64-bit#build_your_app_with_64-bit_libraries

mobile_files/yarn.lock changed. Pinging @jakubgs, @pombeirp, and @corpetty

@asemiankevich could you try this one https://status-im-prs.ams3.digitaloceanspaces.com/StatusIm-190726-151832-03aa67-pr.apk

@asemiankevich could you try this one https://status-im-prs.ams3.digitaloceanspaces.com/StatusIm-190726-151832-03aa67-pr.apk

@flexsurfer https://status-im-prs.ams3.digitaloceanspaces.com/StatusIm-190726-151832-03aa67-pr.apk

in this build installation works on huawei -> but then i see endless spinner on Chats and app is not responsive

on Xiaomi i am stuck on password creation -> app is not responsive (back button for ex) and Next is not active.

Navigation is very slow in this build on my devices, and for example i can end up here when switching between tabs (huawei) - wallet sign phrase in Chat tab.

we've tested version without realm https://status-im-prs.ams3.digitaloceanspaces.com/StatusIm-190729-090042-498654-pr.apk , from this PR #8528 , it still has the same problem

What's the state of this PR and how does this relate to the existing debugging work for arm64? It's been open for quite a while now so I'd suggest closing this particular PR if we can't get it merged this week.

Closing this as I'm working to upgrade to Hermes in #8672, which should fix the issue as shown in https://github.com/PombeirP/arm64-hang-repro-app.

Also created a bug report in RN: facebook/react-native#25970